Skip to main content

Field Placement

Field placement is where you decide where signature and form fields appear on your documents. You position the fields once, on the sample PDF, and the pipeline reprojects that layout onto every live document it processes.


Placing Fields on the Sample

In the wizard's field placer, you work directly on the sample PDF you uploaded:

  1. Pick a field type from the toolbar.
  2. Click to drop it onto the page where it belongs.
  3. Position it by dragging it into place.
  4. Choose the target page: the first page, the last page, or a specific page number.
  5. Assign the recipient who will complete that field.

You can place as many fields as you need, mixing types freely across the document.


Supported Field Types

The placer offers full TurboSign parity, with the same field types you'd use when sending a document manually:

FieldDescription
SignatureThe signer draws or applies their signature.
InitialThe signer initials a page or section.
DateThe date the document is signed.
TextA free-text field the signer fills in.
CheckboxA box the signer checks to confirm or agree.
Full nameThe signer's complete name.
First nameThe signer's given name.
Last nameThe signer's family name.
TitleThe signer's job title.
CompanyThe signer's organization.
EmailThe signer's email address.

Signer-fillable fields (signature, initial, date, text, and checkbox) are completed by the signer as they sign. Identity fields (full name, first name, last name, title, company, and email) capture details about the signer, which they confirm or complete during signing.


All placed fields are required

Every field you place must be completed before a document can finish signing. Place only the fields you genuinely need.


How Placement Travels to Every Document

When you position a field, its location is stored relative to the page rather than as a fixed pixel spot. That means the layout reprojects cleanly onto each live document at runtime, so a signature you placed at the bottom of the last page of your sample lands at the bottom of the last page of every invoice the pipeline processes, even as the content above it changes.


Place against a representative sample

Because placement is relative to the page, the closer your sample matches your real documents' layout, the more precisely fields will land on live runs.


What's Next?